Task Failed Successfully: The Cracked Columbia Takeover and Expulsion
The sputtering 18-hour barricade-aided takeover of Columbia University by Hamas supporters ended last night faster than Humpty Dumpty falling off the wall; of course, the occupier's task failed successfully only after being rightly pushed from the second story ledge of Hamilton Hall by NYPD riot officers. As a graduate of Columbia University, I was chagrined for the students who occupied Hamilton,…
Well…it finally happened…
after teaching beginning photography for over 15 years, I finally did it.
I taught a SHIT class tonight. 😢
I was all out of sorts, my computer didn't want to show the slides properly, I couldn't keep my thoughts straight, it felt like I was unprepared…
Ugh...what an awful feeling…
Hi friends, here's the last #photo from my recent blog post (from my cold #photography - #hiking trip).
This spot was a perfect opportunity to apply ND Filters and some longexposure. I loved …
Recently I've added a cheap hack to the standard #Gentoo invocation for #PyTest to throw errors if unhandled async functions are detected. The goal was to increase our chances of finding packages with missing dependency on dev-python/pytest-asyncio (or another equivalent plugin), or packages disabling plugin autoloading and failing to load such a plugin.
Today, I've gotten a first bug report, regarding dev-python/ipython. I've grepped the sources and confirmed that the package depends on PyTest-AsyncIO, except that it pins to < 0.22. Well, we don't have one that old but let's hope it works anyway. So I've tried adding the dep, `-p asyncio`… and PyTest still apparently couldn't find the plugin. I've scratched my head and tried `PYTEST_PLUGINS` instead — still the same result. What the…?
So I've checked the git repository out, tried with older PyTest-AsyncIO, and indeed the tests worked. Tried with the newest, 0.23.6, and the same issue occurred. I've checked the git history and discovered that the version pin was added because of a buggy 0.22.0 release. However, the issue has been fixed since, the release was yanked and my problem was nothing like that.
So I've investigated more. For some reason, #IPython test suite does not mark tests with `pytest.mark.asyncio` marker directly. Instead, it globally iterates over all test functions, and implicitly adds the marker to all coroutines. This used to work with older versions, but does not work anymore — the test is correctly marked, but for some reason it stops being recognized as a coroutine. So I've made a minimal reproducer and filed a bug.
The key point here is: the (potential) bug went unnoticed for a while now, because of the premature, then obsolete pin in IPython.
#Python
Dark energy and dark matter configurations for wormholes and solitionic hierarchies of nonmetric Ricci flows and $F(R,T,Q,T_{m})$ gravity
Lauren\c{t}iu Bubuianu, Sergiu I. Vacaru, El\c{s}en Veli Veliev, Assel Zhamysheva
https://arxiv.org/abs/2402.19362
Hey friends!
We are just back from another nice 42km #cycling loop. Lots of headwind, lots of up and down and a little mistake in starting the tour at the highest point of the loop. The final, long ascent was a bit... Not so much fun.
But the views were just ace, more streets than yesterday but very few traffic! I was rather happy to have sun cream today.
Just a great Sunday!
Hey friends!
We are just back from another nice 42km #cycling loop. Lots of headwind, lots of up and down and a little mistake in starting the tour at the highest point of the loop. The final, long ascent was a bit... Not so much fun.
But the views were just ace, more streets than yesterday but very few traffic! I was rather happy to have sun cream today.
Just a great Sunday!